Release 10.1A: OpenEdge Development:
Web Services

Creating a Web service procedure object

You map the port type to the procedure object using a syntax similar to how you instantiate a remote persistent procedure:

Syntax

RUN portTypeName [ SET hPortType ] ON SERVER hWebService [ NO-ERROR ] .

For a 4GL remote persistent procedure, you actually execute the procedure by name persistently; for a Web service port type, you invoke the operation using the name of the port type from the WSDL (portTypeName) that defines the operations you want to run. Otherwise, you can set and access a Web service proxy procedure handle (hPortType) the same way as for a remote persistent procedure. Like an AppServer, you use the server object handle bound to the Web service (hWebService) to indicate the remote location to receive Web service requests.

Note the lack of parameters in this statement. Where you might pass parameters when instantiating a remote persistent procedure, you cannot pass any parameters when creating a Web service procedure object, and OpenEdge raises an error if you do so.

A Web service procedure object supports one additional method not used on a proxy procedure object (SET-CALLBACK-PROCEDURE( )). All other attributes and methods on a Web service procedure object work much like they do for any proxy procedure object, or they return Unknown value (?) and empty strings where they have no meaning for a Web service.